Hello,

Your application is missing the Open Source question. Please add that back in and answer accordingly.

Thank you,
Amy Burton

Grant Request is now received. Please do not make any further changes, as it will result in disqualification.

Thank you,
Amy Burton

Hi Amy,

I have updated the grant proposal to include that line with Yes, everything is open source including all the code samples and the text.

I know it's supposed to be one commit per request, so if you need me to cancel this pull request, re-fork the repo, and re-pull as one commit, let me know.

| 0a. | License | Creative Commons BY-SA 4.0 |

Creative Commons BY-SA 4.0 is the current license as written in the proposal. If the ENF would like me to change that, just let me know.

Thanks,

• Douglas

Just saw your second message. I won't make other changes.

Follow up on a request to demonstrate prior work done on the topic:

Minting NFTs from JS
https://gist.github.com/dougbutner/869cc457cfc6b52079fbd77470569335

Reading from NFTs and using it to send payments, then updating NFT Metadata
https://gist.github.com/dougbutner/9ba0b817bfddfa67afb640bbc876117b

My abilities to architect and execute complex systemic builds in Javascript is throughly demonstrated in this video starting around this timestamp:
here: https://youtu.be/coNc4iJB7OM?t=562

The training will be primarily in Node.js, with some explanation in Browser (for WAX) as well

I will try not to use many libraries except Axios, eosjs, waxjs, or the latest Antelope libraries that are available at the time, including wharf when available

This training will be for Javascript, not Typescript, with the reasoning that Typescript is Javascript (superset) but Javascript is not Typescript, so it would be an unneeded idealogical decision that would limit the usefulness of the training to exclude Javascript and only target typescript. Anyone already using Typescript should know they can use it.

I am available for any further questions.

Edit: After talking with Nathan James, we agreed the grant deliverables should include code samples on the Wharf kit tooling. So using Wharfkit, not eosjs / waxjs.

Nathan also clarified that the subject should be EOS, not WAX, which I agreed to with the caveat that I will introduce the material as applicable to all Antelope blockchains in the introduction.

Grants not approved.

Grants not approved.

Thanks. Please try to shorten your feedback time in the future.